No IPv6 after wake from sleep
Hello,
When my MB pro wakes from sleep there is no IPv6 connectivity. In order to restore IPv6 I need to stop/start the Thunderbolt Ethernet adapter (make service inactive/make service active) or reboot.
Details on my configuration:
- OS X 10.9.2
- Thunderbolt Ethernet Adapter used for network connectivity (Wi-Fi OFF)
- Native IPv6 network (not tunneled)
- IPv6 and v4 manual config (no DHCP or SLAAC)
- Dual stack TCP/IP configuration
- IPv4 works
- IPv6 works until MB goes into sleep mode
ifconfig
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether a8:20:xx:xx:xx:xx
inet6 fe80::aa20:xxxx:xxxx:xxxx%en2 prefixlen 64 scopeid 0x4
inet6 2001:xxxx:xxxx:1::2 prefixlen 64
inet 8.x.x.2 netmask 0xffffffc0 broadcast 8.x.x.63
nd6 options=1<PERFORMNUD>
media: autoselect (100baseTX <full-duplex,flow-control>)
status: active
^---- Looks good (to me).
netstat -nr -f inet6
Internet6:
Destination Gateway Flags Netif Expire
default 2001:xxxx:xxxx:1::1 UGc en2
::1 ::1 UHL lo0
2001:xxxx:xxxx:1::2 a8:20:xx:xx:xx UHL lo0
fe80::%lo0/64 fe80::1%lo0 UcI lo0
^--- This looks good too (to me).
Ping my Thunderbolt Ethernet Adapter
PING6(56=40+8+8 bytes) 2001:xxxx:xxxx:1::2 --> 2001:xxxx:xxxx:1::2
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=0 hlim=64 time=0.129 ms
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=1 hlim=64 time=0.233 ms
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=2 hlim=64 time=0.225 ms
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=3 hlim=64 time=0.227 ms
^--- Yay!
Ping the default route
PING6(56=40+8+8 bytes) 2001:xxxx:xxxx:1::2 --> 2001:xxxx:xxxx:1::1
ping6: sendmsg: No route to host
ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1
^--- Boo 😟
This causes problems for IPv4 as well because apps like Firefox and Safari try using the IPv6 DNS servers and give up before falling back to the IPv4 servers. So this problem breaks more than IPv6.
Is this a bug or do I have something misconfigured?
Thanks.
--Tom
Mac Pro, OS X Mavericks (10.9.2)
